Updated the bootstrap process to allow users to bypass the installation check. This change prevented the command from failing when Pipelines as Code is already present in the cluster, enabling users to skip the automatic installation step when it is not required.

tested as working on openshift cluster:

before:

%   tkn pac bootstrap github-app \
    -n pipelines-as-code \
    --skip-install \
    --route-url "https://$(oc get route pipelines-as-code-controller -n pipelines-as-code -o jsonpath='{.spec.host}')" \
    --github-application-name "blahblah \
    --github-organization-name org
Error: pipelines as Code is already installed, please pass --force-install to override existin

after:

working

Closes #2708

📝 Description of the Change

🔗 Linked GitHub Issue

Fixes #

🧪 Testing Strategy

• Unit tests
• Integration tests
• End-to-end tests
• Manual testing
• Not Applicable

🤖 AI Assistance

AI assistance can be used for various tasks, such as code generation,
documentation, or testing.

Please indicate whether you have used AI assistance
for this PR and provide details if applicable.

• I have not used any AI assistance for this PR.
• I have used AI assistance for this PR.

✅ Submitter Checklist

• 📝 My commit messages are clear, informative, and follow the project's How to write a git commit message guide. The Gitlint linter ensures in CI it's properly validated
• ✨ I have ensured my commit message prefix (e.g., fix:, feat:) matches the "Type of Change" I selected above.
• ♽ I have run make test and make lint locally to check for and fix any
  issues. For an efficient workflow, I have considered installing
  pre-commit and running pre-commit install to
  automate these checks.
• 📖 I have added or updated documentation for any user-facing changes.
• 🧪 I have added sufficient unit tests for my code changes.
• 🎁 I have added end-to-end tests where feasible. See README for more details.
• 🔎 I have addressed any CI test flakiness or provided a clear reason to bypass it.
• If adding a provider feature, I have filled in the following and updated the provider documentation:
  • GitHub App
  • GitHub Webhook
  • Gitea/Forgejo
  • GitLab
  • Bitbucket Cloud
  • Bitbucket Data Center